You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@arturobernalg Do I understand it correctly this change-set implements a subset of RFC 8470, namely the retry part, and does not implement early data requests at all?
@arturobernalg Do I understand it correctly this change-set implements a subset of RFC 8470, namely the retry part, and does not implement early data requests at all?
Yes, that’s correct: this change-set only implements the HTTP-side handling of 425 Too Early (single retry, and the retry is marked to avoid early data). It does not implement sending requests in TLS 1.3 0-RTT early data.
arturobernalg
changed the title
Implements RFC 8470 “Using Early Data in HTTP”
HTTP 425 Too Early retry handling (RFC 8470) + Retry-After support for 429/503
Jan 17, 2026
@arturobernalg Do I understand it correctly this change-set implements a subset of RFC 8470, namely the retry part, and does not implement early data requests at all?
Yes, that’s correct: this change-set only implements the HTTP-side handling of 425 Too Early (single retry, and the retry is marked to avoid early data). It does not implement sending requests in TLS 1.3 0-RTT early data.
@arturobernalg This makes no sense. How would we get 425 status if we are not able to generate early data requests at all?
@arturobernalg Do I understand it correctly this change-set implements a subset of RFC 8470, namely the retry part, and does not implement early data requests at all?
Yes, that’s correct: this change-set only implements the HTTP-side handling of 425 Too Early (single retry, and the retry is marked to avoid early data). It does not implement sending requests in TLS 1.3 0-RTT early data.
@arturobernalg This makes no sense. How would we get 425 status if we are not able to generate early data requests at all?
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
arturobernalg
commented
arturobernalg
force-pushed
the
early-data
branch
2 times, most recently
from
